# Page Not Found

The URL `Y�]�������[XY�K�M�]��[̑Y[�T�ٌ�` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [노트북 AS 기간 확인 하기](https://ssv.skill.or.kr/tips/as-check-warranty.md)
- [Docker 시스템 취약점 점검 가이드](https://ssv.skill.or.kr/cloud-security/docker-security-vulnerability.md)
- [[DB] MS-SQL 시스템 취약점 점검 가이드](https://ssv.skill.or.kr/cloud-security/db-mssql-security-vulnerability.md)
- [[DB] MY-SQL 시스템 취약점 점검 가이드](https://ssv.skill.or.kr/cloud-security/db-mysql-security-vulnerability.md)
- [IIS 시스템 취약점 점검 가이드](https://ssv.skill.or.kr/cloud-security/iis-security-vulnerability.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ssv.skill.or.kr/tips/as-check-warranty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://ssv.skill.or.kr/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://ssv.skill.or.kr/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/tips/as-check-warranty.md`).

You may also use `Accept: text/markdown` header for content negotiation.